Specifies whether rail discharge processing is handled on N4 or XPS.
Setting to N4 reduces dependencies on XPS. This is the default.
Setting to XPS_Server reverts back to N4 sending Bento requests to XPS to complete rail discharges. You would only select XPS_Server if you encounter problems with N4 rail move processing. See Rolling back N4 vessel and rail move processing to XPS (on page 1) for more rollback information.
When Scaled XD clients are not available, XPS accepts the Scaled XD decking requests. However, this is based on the value set for the N4 setting ARGOXPS013 (XPS_ACCEPTS_SCALED_XD_DECKING_REQUESTS).
If ARGOXPS013 = True:
Scaled XD decking requests will be sent to the XPS server if Scaled XD clients are not available.
If ARGOXPS013 = False:
Decking requests are not sent to XPS, which means that the container will not be decked.
If the containers in the decking request have a valid planned position, that is from pre-decking, the planned position is retained.
If the containers in the decking request do not have a planned position, the containers will fail to deck. In the case of a gate transaction, XPS will not create a plan for the fail to deck containers. However, the gate transaction will be moved into Trouble status, depending on the gate configuration.